Skip to content

Conversation

@flip111
Copy link

@flip111 flip111 commented Jun 6, 2025

Hello

When I installed odpdown with uv or pip, the odpdown command wasn't being created in my path.

It looks like the build system was getting confused by the project having both an odpdown.py file and an odpdown/ directory.

This PR fixes it by explicitly telling the PDM build tool to use the odpdown/ directory, which resolves the ambiguity. It also adds the missing [project.scripts] definition.

This approach fixes the modern packaging while leaving the old odpdown.py file in place for anyone who might still be using it directly.

Hope this helps!

The odpdown command-line script was not being created on installation.

This was caused by two issues:
1. The build system was getting confused by the ambiguous project
   structure (both `odpdown.py` and an `odpdown/` directory).
2. The `pyproject.toml` was missing the `[project.scripts]` definition.

This commit resolves the ambiguity by explicitly telling the PDM build
backend to only include the `odpdown/` directory in the final package.
It also adds the missing script definition.

This allows the legacy `odpdown.py` file to remain in the repository
for any users who may depend on it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant